On an Exchange 2007 / Server 2003 / AD 2003 network I have a user with a mailbox. This user requires access to their email via POP3 from home and they have it. The problem is that they cannot send email this way through our server. They get an error along the lines of "550 5.7.1 Client does not have permissions to send as this sender". In the office using Outlook everything is fine. After much searching and frustration I found that this particular user did not have "Send As" permission to their own mailbox. So I went via EMC and set "Send As" for "SELF" and the permission applied and everything was great. It stops working after a while and the permission disappears. I did a lot of looking about and it seems like this is related somehow to the user being a member of a protected group and having their permissions reset by the PDC every hour. This user is not a member of any protected groups (I can't comment on previous membership as this network/account is older then me). However it is a native 2003 domain and there was no migration from a previous exchange server to 2007. Is there anyway to fix this without modifying the adminSDholder thing with ADSI edit (some sort of flag I can trip on the users account to get him back to a regular user?) I will leave out all my rants about the 'features' that would deny a user the ability to "SEND AS" their own mailbox.. *grumble* Thank you for your help!

On Wed, 15 Dec 2010 00:35:10 +0000, Darrkon wrote: > > >On an Exchange 2007 / Server 2003 / AD 2003 network I have a user with a mailbox. > >This user requires access to their email via POP3 from home and they have it. The problem is that they cannot send email this way through our server. They get an error along the lines of "550 5.7.1 Client does not have permissions to send as this sender". In the office using Outlook everything is fine. > >After much searching and frustration I found that this particular user did not have "Send As" permission to their own mailbox. So I went via EMC and set "Send As" for "SELF" and the permission applied and everything was great. > >It stops working after a while and the permission disappears. I did a lot of looking about and it seems like this is related somehow to the user being a member of a protected group and having their permissions reset by the PDC every hour. This user is not a member of any protected groups (I can't comment on previous membership as this network/account is older then me). However it is a native 2003 domain and there was no migration from a previous exchange server to 2007. > >Is there anyway to fix this without modifying the adminSDholder thing with ADSI edit (some sort of flag I can trip on the users account to get him back to a regular user?) If the user isn't a member of any protected groups then you should be able to remove the adminCount property (or just set the value to zero) from the user. If the adminCount is set to 1 a couple of hours later then the user is a member of a protected group -- perhaps indirectly. >I will leave out all my rants about the 'features' that would deny a user the ability to "SEND AS" their own mailbox.. *grumble* What about the rants concerning users with elevated privileges having a mailbox? :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, The following article would be helpful, please see section "Proxying and Redirection for Outlook Web App " http://technet.microsoft.com/en-us/library/bb310763.aspx Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Thanks I think that's what it is.. I did some more reading based on what you said then some snooping around in AD and found that one of our common groups for users was a member of Account Operators. Now we need to figure out if removing our group from Account Operators is going to break anything before I can give this a go.. but at least now I know what the problem is. Once again, thank you for your reply and help! :)